Skip to content

Remove label management from Issue-Triage - #5013

Merged
cheenamalhotra merged 1 commit into
mainfrom
dev/cheena/remove-triage-labeling
Nov 6, 2026
Merged

cheenamalhotra merged 1 commit into
mainfrom
dev/cheena/remove-triage-labeling

Conversation

@cheenamalhotra

Copy link
Copy Markdown
Member

Description

Issue-Triage failed because label changes were queued before its summary comment. Make the workflow comment-only by removing label safe outputs and label-management instructions, and reject any label operations in the publication validator.

Author follow-ups now use the latest workflow summary's Environment row instead of a Waiting for Author label. This means author comments start the agent even without that label; runs with no outstanding details or no new information exit without posting. Area classification remains a recommendation only.

Regenerated the executable workflow lock file and updated the validator tests and their documentation. No public API or driver behavior changes; localization is not applicable.

Issues

Addresses the failed Issue-Triage run.

Testing

  • node --test .github\scripts\tests\validate-triage-output.test.cjs - passed all 26 tests. Covers comment-only summaries across triage scenarios, rejected label operations, unchanged output files, and compiled workflow wiring.
  • gh aw compile - succeeded with no warnings; a second compilation produced an identical lock file.
  • git diff --check - passed.

A live Issue-Triage run was not performed. Driver unit/integration tests are not applicable to this workflow-only change.

  • Tests added or updated
  • Public API changes documented (not applicable)
  • Verified against customer repro (not applicable; live workflow not rerun)
  • Ensure no breaking changes introduced (driver APIs unchanged; workflow activation change described above)

Guidelines

Please review the contribution guidelines before submitting a pull request:

Keep triage comment-only and use the latest summary for author follow-ups. Update validation, regressions, and the generated workflow.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Missing PR/head identifiers and trusted immutable policy references prevent verification of current-head feedback, checks, and follow-up routing.

No open issues 🎉

What changed in this PR

Makes Issue-Triage comment-only, removing label operations that caused publication failures. Author follow-ups now use the latest workflow summary to identify missing environment details. Driver behavior and public APIs are unchanged.

Changes:

  • Removes label tools and instructions; keeps area classification as a summary recommendation.
  • Rejects label operations before publication and validates queued output without modifying it.
  • Regenerates the executable workflow and updates regression tests and documentation.
File Description
.github/​workflows/​issue-triage.md Removes label management and introduces summary-based follow-up routing.
.github/​workflows/​issue-triage.lock.yml Regenerates runtime configuration without label tools or label-based activation.
.github/​scripts/​validate-triage-output.cjs Rejects label operations and removes queue reordering and file rewriting.
.github/​scripts/​tests/​validate-triage-output.test.cjs Covers comment-only validation, label rejection, unchanged files, and compiled wiring.
.github/​scripts/​tests/​README.md Documents updated validation coverage and summary-based follow-up state.

Review effort: Balanced

@paulmedynski paulmedynski modified the milestones: 8.0.0-preview1, 8.0.0 Nov 6, 2026
@cheenamalhotra
cheenamalhotra merged commit f57988e into main Nov 6, 2026
22 of 25 checks passed
@cheenamalhotra
cheenamalhotra deleted the dev/cheena/remove-triage-labeling branch November 6, 2026 17:29
@github-project-automation github-project-automation Bot moved this from To triage to Done in SqlClient Board Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

7 participants